Finding ID | Version | Rule ID | IA Controls | Severity |
---|---|---|---|---|
V-89951 | VRAU-TC-000190 | SV-100601r1_rule | Medium |
Description |
---|
After a security incident has occurred, investigators will often review log files to determine what happened. tc Server HORIZON must create a log entry when users access the system, and the system authenticates the users. The logs must contain information about user sessions to include what type of event occurred, when (date and time) events occurred, where within the server the events occurred, the client source of the events, the outcome (success or failure) of the event, the identity of the user/subject/process associated with the event. As a Tomcat derivative, tc Server can be configured with an AccessLogValve. A Valve element represents a component that can be inserted into the request processing pipeline. The pattern attribute of the AccessLogValve controls which data gets logged. The %h parameter will record the remote hostname or IP address that sent the request; i.e. the source of the event. |
STIG | Date |
---|---|
VMware vRealize Automation 7.x tc Server Security Technical Implementation Guide | 2018-10-12 |
Check Text ( C-89643r1_chk ) |
---|
At the command prompt, execute the following command: tail /storage/log/vmware/horizon/localhost_access_log.YYYY-MM-dd.txt Note: Substitute the actual date in the file name. If the source IP of events are not being recorded, this is a finding. |
Fix Text (F-96693r1_fix) |
---|
Navigate to and open /opt/vmware/horizon/workspace/conf/server.xml. Navigate to and locate Configure the Note: The "AccessLogValve" should be configured as follows: pattern="%h %l %u %t "%r" %s %b" prefix="localhost_access_log." suffix=".txt"/> |